Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3

4.4.2.20547 HL7 v3 Value Set ProvenanceEventCurrentState

Vocabulary

Work Group

Maturity Level: N/A

External

Use Context: Any

This value set (http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState) is defined as part of HL7 v3.

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState

Version:

2014-08-07

Name:

v3.ProvenanceEventCurrentState

Title:

V3 Value SetProvenanceEventCurrentState

Definition:

Specifies the state change of a target Act, such as a document or an entry, from its previous state as a predecessor Act. For example, if the target Act is the result of a predecessor Act being "obsoleted" and replaced with the target Act, the source ProvenanceEventCurrentState Act code would be "obsoleted".

OID:

2.16.840.1.113883.1.11.20547 (for OID based terminology systems)

Source Resource

XML / JSON

This value set is not currently used

4.4.2.20547.1 Content Logical Definition

This value set includes codes from the following code systems:

Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState-AS
Import all the codes that are contained in http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState-DC

4.4.2.20547.2 Expansion

This expansion generated 01 Nov 2019

This value set contains 11 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion version 2018-08-12, http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState-DC version 2014-08-07, http://terminology.hl7.org/ValueSet/v3-ProvenanceEventCurrentState-AS version 2014-08-07, http://terminology.hl7.org/CodeSystem/v3-ActStatus version 2018-08-12

Code	System	Display	Definition
aborted	http://terminology.hl7.org/CodeSystem/v3-ActStatus	aborted	The Act has been terminated prior to the originally intended completion.
cancelled	http://terminology.hl7.org/CodeSystem/v3-ActStatus	cancelled	The Act has been abandoned before activation.
completed	http://terminology.hl7.org/CodeSystem/v3-ActStatus	completed	An Act that has terminated normally after all of its constituents have been performed.
new	http://terminology.hl7.org/CodeSystem/v3-ActStatus	new	An Act that is in the preparatory stages and may not yet be acted upon
nullified	http://terminology.hl7.org/CodeSystem/v3-ActStatus	nullified	This Act instance was created in error and has been 'removed' and is treated as though it never existed. A record is retained for audit purposes only.
obsolete	http://terminology.hl7.org/CodeSystem/v3-ActStatus	obsolete	This Act instance has been replaced by a new instance.
AU	http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion	authenticated	A completion status in which a document has been signed manually or electronically by one or more individuals who attest to its accuracy. No explicit determination is made that the assigned individual has performed the authentication. While the standard allows multiple instances of authentication, it would be typical to have a single instance of authentication, usually by the assigned individual.
DI	http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion	dictated	A completion status in which information has been orally recorded but not yet transcribed.
DO	http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion	documented	A completion status in which document content, other than dictation, has been received but has not been translated into the final electronic format. Examples include paper documents, whether hand-written or typewritten, and intermediate electronic forms, such as voice to text.
LA	http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion	legally authenticated	A completion status in which a document has been signed manually or electronically by the individual who is legally responsible for that document. This is the most mature state in the workflow progression.
UC	http://terminology.hl7.org/CodeSystem/v3-DocumentCompletion	unsigned completed document	A completion status where the document is complete and there is no expectation that the document will be signed.